chore(deps): update fsfe/reuse docker tag to v5.1.1 #16
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
5.0.2→5.1.1Release Notes
fsfe/reuse-tool (fsfe/reuse)
v5.1.1Compare Source
Fixed
(#1191)
was introduced in v5.0.0. Strings that were already translated before the
release of v5.0.0 are now translated again. (#1216)
v5.1.0Compare Source
Added
.dtd(#1141).gperf(#1131).erland.hrl, leex and yecc Erlang parser generators.xrland.yrl(#1117).exand.exs) (#1117).gleam) (#1117).lean,.olean, and.ilean) (#1188)--jsonflag to thesupported-licensessubcommand. (#1187)Changed
Cargo.lockto uncommentable. (#1169)reuse annotatepreviously would insert a newline after a header, which isnot always a desirable behavior. Instead of inserting a newline,
reuse annotatewill now respect the existing whitespace of the file wherethe header is being placed. When the license header is being added to a file
for the first time, a space will be added after the license, but subsequent
updates to the header will leave the whitespace alone. (#1136)
spdx-license-list-datato v3.27.0.Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.